Common Errors Found When Ordering Compute Jobs
This page provides a list of common errors that users might encounter when ordering compute jobs, along with potential solutions.
Unable to get output file from compute job
This error commonly occurs after running a compute-to-data job and accessing it under the 'Purchased Assets- Compute Jobs' tab on the marketplace. The job status will show either 'Failed', 'Incomplete', and/or no output file under the column 'Get Results'. The algorithm/dataset may be incompatible for the compute job.
How can this be resolved? As a Data Consumer, ensure you are selecting the appropriate data to compute and try again. If the error persists, contact and wait until the Data Provider addresses the issue.
Unable to start compute job
This error occurs when a user tries to run compute jobs. It usually happens because the dataset/algorithm is in use and running.
Message: “You have a compute job running with this dataset. Please try again later once the compute job is complete.“
How can this be resolved? Rerun the job after some time once the asset has completed running their task.
Unable to rerun job
This error occurs when a user tries to rerun compute jobs.
How can this be resolved? Rerun the job after some time.
Unable to order again
This error occurs when a user tries to rerun a compute job.
How can this be resolved? Try to order again.
Aggregate status running too long
This error happens when the user orders a multiple compute job, but the status is still 'running' after a while.
How can this be resolved? Wait for the aggregate job to complete. Run another aggregate job and see if the error persists.